Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • 4 452-labs
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Doug Woos
  • 452-labs
  • Wiki
  • Lab 3

Lab 3 · Changes

Page history
Various fixes authored Mar 24, 2017 by Ellis Michael's avatar Ellis Michael
Hide whitespace changes
Inline Side-by-side
Lab-3.md
View page @ 9cb9f462
......@@ -93,7 +93,7 @@ complete the labs individually.
Do a `git pull` to get the latest lab software. You should already have to
skeleton code for this lab in the `paxos` directory:
```sh
```
$ cd $GOPATH/src/paxos
$ go test
Single proposer: --- FAIL: TestBasic (5.02 seconds)
......@@ -113,7 +113,7 @@ First you'll implement a Paxos library. paxos.go contains descriptions of the
methods you must implement. When you're done, you should pass all the tests in
the paxos directory (after ignoring Go's many complaints):
```sh
```
$ cd $GOPATH/src/paxos
$ go test
Test: Single proposer ...
......@@ -405,9 +405,9 @@ will either discover the previously agreed-to value, or cause agreement to
happen. Think about what value would be reasonable to pass to `Start()` in this
situation.
**Hint:** When the test fails, check for gob error (e.g. `rpc: writing response:
gob: type not registered for interface ...`) in the log because go doesn't
consider the error fatal, although it is fatal for the lab.
**Hint:** When the test fails, check for gob error (e.g.
`rpc: writing response: gob: type not registered for interface ...`) in the log
because go doesn't consider the error fatal, although it is fatal for the lab.
**Hint:** part B should take around 200 lines of code.
......
Clone repository
  • Lab 1
  • Lab 2
  • Lab 3
  • Lab 4
  • Home
  • submission