Get desktop application:
View/edit binary Protocol Buffers messages
credentials required to create an S3 Client and upload artifacts to it
Used in:
Used in:
Used in:
(message has no fields)
Used in:
Responses to the client commands
This configuration is done once, when SMELT is initialized The client should provide this when creating an smelt handle
Used in:
Should be an absolute path
number of slots the entire executor has -- analogous to job slots in make
configures how we profile commands
If true, we ignore the non test commands
If true, we do not transmit stdout from the server
if true, smelt execution will prepare the workspace to run tests in another stage this is useful for splitting the work between a build and test stage
if true, all commands will have their environment variables sandboxed
Used in:
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
if we enable simple profiling
Used in:
only memory and cpu
Used in:
Used in:
Used in:
Used in:
Eventually, perhaps we should encode this as info in protobuf not today babey
Used in:
Just a list of Commands, serialized as json
Populate info for the slurm server This is configured from the end-user side. if these data is not provided, then smelt will execute `whoami` to derive hostname and will let the OS select the port
Used in:
this is the hostname used by smelt and all workers, by default
This is port supplied to each worker a. Sometimes you'll have a proxy in front of your smelt server to make deployment easier. e.g. this is practical for deploying in non-LAN networking environments
Used in:
Clone of Bollard proto message Ulimit
Used in: