| Commit message (Collapse) | Author | Age | Lines |
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The Azure website has proven to not be reliable for displaying the
JUnit output. Furthermore, some may simply prefer the format of the
output in the terminal over the JUnit representation on the Azure site.
Nevertheless, the JUnit output isn't that bad (when there's actually
a lint error) so it will remain for now. It also provides historical
statistics on occurrences of errors, which is kind of cool, I guess...
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since #62, the dependencies have been installed to the system
interpreter. Therefore, it's not necessary to run through pipenv to
ensure the commands run through an activated virtual environment.
This should also fix pipenv run creating a virtual environment. It seems
it cannot tell when it should be using the system interpreter. It
probably wasn't designed for that anyway i.e. the intent was to run
commands directly in such case, which is what this PR will do.
|
| | |
|
| |
| |
| |
| | |
The array shouldn't be expanded when testing with -v.
|
| |
| |
| |
| |
| |
| | |
The script may need to use the master commit several times. The easiest
way to implement the cache was to just cache the response rather than
the commit hash.
|
| |
| |
| |
| | |
Hyphens are disallowed so they are replaced with underscores.
|
| |
| |
| |
| |
| | |
* Remove duplicate build steps
* Move push steps to a separate YAML file
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Build if the base changed or the venv changed and the base cannot be
pulled.
|
| | |
|
| |
| |
| |
| |
| |
| | |
It was initially used to enable access to variables across jobs, but
the jobs will eventually be consolidated into one so output variables
will no longer be needed.
|
| |
| |
| |
| | |
Avoids type casting ambiguity and weirdness.
|
| |
| |
| |
| |
| | |
This change allows for the venv image to be pushed since it won't be
built with dev dependencies.
|
| | |
|
| |
| |
| |
| | |
Splitting steps into several files makes the YAML more maintainable.
|
| |
| |
| |
| | |
* Use inherit_errexit in check_dockerfiles.sh
|
| | |
|
| | |
|
| |
| |
| |
| | |
This reverts commit c9e807eb8e0e940d1b4acde17d8699d85582569f.
|
| | |
|
| | |
|
| | |
|
| | |
|
|\| |
|
| |\
| | |
| | |
| | |
| | | |
python-discord/bug/ci/61/python-symlink-not-resolving
Install Pipfile into system interpreter
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A virtual environment is redundant in the context of deployment. It
just increases the size and build time of the image.
* Replace venv with system interpreter
* Mount Python binaries in /usr/local/bin in NsJail
* Fix #61: Python symlink in venv not resolving
* Re-lock Pipfile because it wasn't up to date according to
pipenv install --deploy
|
| |\
| | |
| | | |
Configure a proper chroot jail for NsJail
|
| | |\
| | |/
| |/| |
|
| | | |
|
| | | |
|
| | |
| | |
| | | |
Co-Authored-By: Sebastiaan Zeeff <[email protected]>
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This is a test for #53, which fixed numpy failing to import due to
using multiple threads by default.
|
| | | |
|
| | |
| | |
| | |
| | | |
Co-authored-by: 0xf0f <[email protected]>
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
devfs and sysfs were problematic since they were being mounted as
tmpfs, which is r/w. For example, the Python process could write to
cgroups. Now, only what is needed to run Python gets mounted. This
boils down to the venv itself and some shared libraries Python needs.
* Use a config file for NsJail instead of command-line options
* Map 65534 (nobody) user & group inside the user namespace to 65534
outside the namespace rather than mapping to current uid/guid (which
was 0 AKA root)
|
| |/ |
|
| |\
| | |
| | | |
Limit numpy to using 1 thread
|
| |/ |
|
| |\
| | |
| | | |
CI: fix incorrect CWD for check script
|
| |/ |
|
| |\
| | |
| | | |
Add external libraries and update image
|
| | | |
|
| | | |
|