summaryrefslogtreecommitdiff
path: root/test/end-to-end/serve-service
AgeCommit message (Collapse)Author
2023-12-12test: Check tc sharding if 'just serve' acts also as 'just execute'Paul Cristian Sarbu
2023-12-05test: Check remote build via just servePaul Cristian Sarbu
2023-11-16test: Check that serve service works in compatible modePaul Cristian Sarbu
Added compatibility envariable to the with_serve rule, guarded tests using --fetch-absent such that they run only in native mode, and made all serve-service tests aware of the compatibility flag.
2023-11-16remote-execution-endpoint: fall back to remote-serve-endpointAlberto Sartori
If only the `--remote-serve-endpoint` option is specified on the command line, the `--remote-execution-endpoint` is also set to the given value. This makes the spawning and usage of just-execute consistent. When just-serve is started, if no remote execution endpoint is provided, the same process will also act as a just-execute instance. With the current patch, the client can thus only write, on command line, the remote serve address, avoiding the repetition of the same address for two different options.
2023-11-16end-to-end serve-target-cache-hit: test the failure if...Alberto Sartori
...the client and serve use two different remote execution endpoints fixup test
2023-11-15just-serve: add end-to-end testsAlberto Sartori
serve_target_remote_build.sh should be updated once just-serve can orchestrate the remote build