| Commit message (Collapse) | Author | Age | Lines | ||
|---|---|---|---|---|---|
| ... | |||||
| * | | | Fix echo | 2019-06-29 | -1/+1 | ||
| | | | | |||||
| * | | | Remove constant | 2019-06-29 | -3/+0 | ||
| | | | | |||||
| * | | | Echo $(PREV_BUILD) | 2019-06-29 | -4/+6 | ||
| | | | | |||||
| * | | | Run-time format expression | 2019-06-29 | -1/+1 | ||
| | | | | |||||
| * | | | Try an expression | 2019-06-29 | -4/+4 | ||
| | | | | |||||
| * | | | Does the variable get overwritten? | 2019-06-29 | -1/+10 | ||
| | | | | |||||
| * | | | Set variable beforehand | 2019-06-29 | -0/+3 | ||
| | | | | |||||
| * | | | Try for V2 again | 2019-06-29 | -3/+3 | ||
| | | | | |||||
| * | | | Use variable for build ID pls work | 2019-06-29 | -1/+1 | ||
| | | | | |||||
| * | | | Print Base ID | 2019-06-29 | -1/+2 | ||
| | | | | |||||
| * | | | Explicit and specific | 2019-06-29 | -1/+1 | ||
| | | | | |||||
| * | | | Let's Get Specific 2: Electric Boogaloo | 2019-06-29 | -2/+2 | ||
| | | | | |||||
| * | | | Explicit buildId | 2019-06-29 | -1/+1 | ||
| | | | | |||||
| * | | | Fuck v2 I'll switch to it when they properly document it... | 2019-06-29 | -5/+5 | ||
| | | | | |||||
| * | | | Wtf... try v2 | 2019-06-29 | -2/+2 | ||
| | | | | |||||
| * | | | DownloadPipelineArtifact | 2019-06-29 | -1/+1 | ||
| | | | | |||||
| * | | | Screw the base variable | 2019-06-29 | -6/+4 | ||
| | | | | |||||
| * | | | What's your problem? | 2019-06-29 | -1/+1 | ||
| | | | | |||||
| * | | | Explicitly specify build id | 2019-06-29 | -8/+9 | ||
| | | | | |||||
| * | | | Output var | 2019-06-29 | -10/+6 | ||
| | | | | |||||
| * | | | aaaaaaaaaaaaaaaaaa | 2019-06-29 | -2/+2 | ||
| | | | | | | | | | | | | | !!! | ||||
| * | | | Try quoting the var | 2019-06-29 | -1/+1 | ||
| | | | | |||||
| * | | | Try to fix vars | 2019-06-29 | -0/+4 | ||
| | | | | |||||
| * | | | Echo variables | 2019-06-29 | -10/+18 | ||
| | | | | |||||
| * | | | Get previous build ID | 2019-06-29 | -20/+52 | ||
| | | | | |||||
| * | | | Yes | 2019-06-29 | -2/+4 | ||
| | | | | |||||
| * | | | Check contents of artifact | 2019-06-29 | -0/+4 | ||
| | | | | |||||
| * | | | Let's get specific | 2019-06-29 | -1/+1 | ||
| | | | | |||||
| * | | | Try to fix task inputs | 2019-06-29 | -3/+3 | ||
| | | | | |||||
| * | | | Maybe v1 will work | 2019-06-29 | -2/+2 | ||
| | | | | |||||
| * | | | DownloadPipelineArtifact | 2019-06-29 | -0/+12 | ||
| | | | | | | | | | | | | | pls work | ||||
| * | | | Use v1 of task | 2019-06-29 | -1/+1 | ||
| | | | | |||||
| * | | | Use task instead | 2019-06-29 | -2/+4 | ||
| | | | | |||||
| * | | | Test artifact publishing | 2019-06-29 | -156/+14 | ||
| | |/ |/| | |||||
| * | | Merge pull request #31 from python-discord/testing | 2019-06-29 | -191/+364 | ||
| |\ \ | | | | | | | NsJail Tests | ||||
| | * | | Use write_text() and fix codec names | 2019-06-29 | -5/+3 | ||
| | | | | |||||
| | * | | Test that the file system is mounted as read only | 2019-06-27 | -0/+10 | ||
| | | | | |||||
| | * | | Disable swap memory | 2019-06-27 | -3/+7 | ||
| | | | | |||||
| | * | | Fix error when setting swap limit on a system that has it disabled | 2019-06-27 | -3/+9 | ||
| | | | | | | | | | | | | | | | | The error happens when either CONFIG_MEMCG_SWAP or CONFIG_MEMCG_SWAP_ENABLED is disabled in the kernel. | ||||
| | * | | Disable memory swapping and add a memory limit test | 2019-06-26 | -8/+34 | ||
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | If memory swapping was enabled locally, the memory test would fail. Explicitly disabling swapping also removes reliance on the assumption that it'll be disabled in production. * Add a constant for the maximum memory * Simplify the timeout test; it'd otherwise first run out of memory now | ||||
| | * | | Don't generate an HTML report because Azure already does it | 2019-06-22 | -2/+1 | ||
| | | | | | | | | | | | | | See microsoft/azure-pipelines-tasks#9704 | ||||
| | * | | Remove -it options from docker exec | 2019-06-22 | -3/+3 | ||
| | | | | |||||
| | * | | Add missing steps key | 2019-06-22 | -0/+1 | ||
| | | | | |||||
| | * | | Run linting & tests in a container | 2019-06-22 | -14/+28 | ||
| | | | | |||||
| | * | | Fix syntax errors in azure-pipelines.yml | 2019-06-22 | -6/+7 | ||
| | | | | | | | | | | | | | | | | * Add succeededOrFailed condition to code coverage publish task * Rename test publish task for unit tests | ||||
| | * | | Add CI steps for running & publishing tests | 2019-06-22 | -17/+49 | ||
| | | | | |||||
| | * | | Fix venv being included in coverage when testing in a container | 2019-06-22 | -4/+7 | ||
| | | | | | | | | | | | | | * Exclude DEBUG checks from coverage reports | ||||
| | * | | Add a NsJail log parser test | 2019-06-22 | -3/+33 | ||
| | | | | | | | | | | | | | | | | * Add support for debug level to log regex * Change type annotation of log_parse to Iterable | ||||
| | * | | Rewrite NsJail tests | 2019-06-22 | -58/+80 | ||
| | | | | | | | | | | | | | | | | | | | * Fix SIGSEGV test * Add embedded null byte test * Return None for stderr when there's a ValueError | ||||
| | * | | Capture NsJail logs from stdout if NsJail fails to parse cmd args | 2019-06-22 | -3/+9 | ||
| | | | | | | | | | | | | | Fixes #30 | ||||